SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 49446: Errors occur when you attempt to define a new source code repository or modify a stored process using SAS® Enterprise Guide® 5.1

DetailsHotfixAboutRate It

Using either of two SAS Enterprise Guide hot fixes can lead to errors in defining new source code repositories on a UNIX server and might also lead to errors when you attempt to modify an existing stored process.

This SAS Note describes both situations and how to work around them.

The two hot fixes are:

  • SAS Enterprise Guide 5.1 (5.100.0.13037) Hot Fix 10 and
  • SAS Enterprise Guide 5.1 (5.100.0.13078) Hot Fix 11.

Error Occurs When Defining New Source Code

When you connect to a UNIX server and attempt to define a new source code repository within the stored process wizard or manager, this error occurs:

Addition of Directory Path Failed While attempting to create the directory path '/path to some location' on the file system associated with logical server 'SASApp - Logical Stored Process Server' the following error was encountered: Physical file does not exist, /<path to config dir>/Lev1/SASApp/<start of new path above>.
To work around this issue, follow these steps:
  1. Start SAS® Management Console.
  2. Click the Folders tab and navigate to any stored process.
  3. Right-click a stored process and then select ► Properties ► Execution ► Manage....
  4. In the Manage... window, enter the path to the folder in which you would like users to save .sas files for stored processes.

Error Occurs When Modifying a Stored Process

When you attempt to modify an existing stored process, the following error might occur:

image label

If you click Yes and continue, this error is generated:

image label

The problem occurs because the source code repository paths are invalid. The SAS Enterprise Guide stored process manager is incorrectly reconstructing the source code paths. With the incorrect source code paths, the stored process manager fails to locate the .sas file associated with the stored process, which causes the "SAS Code" section of the stored process manager to display a blank window.

This issue does not affect the execution of the stored process.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Enterprise GuideMicrosoft® Windows® for x645.16.19.4 TS1M0
Microsoft Windows 8 Pro5.16.19.4 TS1M0
Microsoft Windows Server 2003 Datacenter Edition5.16.19.4 TS1M0
Microsoft Windows Server 2003 Enterprise Edition5.16.19.4 TS1M0
Microsoft Windows Server 2003 Standard Edition5.16.19.4 TS1M0
Microsoft Windows Server 2003 for x645.16.19.4 TS1M0
Microsoft Windows Server 20085.16.19.4 TS1M0
Microsoft Windows Server 2008 for x645.16.19.4 TS1M0
Microsoft Windows Server 20125.16.19.4 TS1M0
Microsoft Windows XP Professional5.16.19.4 TS1M0
Windows 7 Enterprise 32 bit5.16.19.4 TS1M0
Windows 7 Enterprise x645.16.19.4 TS1M0
Windows 7 Home Premium 32 bit5.16.19.4 TS1M0
Windows 7 Home Premium x645.16.19.4 TS1M0
Windows 7 Professional 32 bit5.16.19.4 TS1M0
Windows 7 Professional x645.16.19.4 TS1M0
Windows 7 Ultimate 32 bit5.16.19.4 TS1M0
Windows 7 Ultimate x645.16.19.4 TS1M0
Windows Vista5.16.19.4 TS1M0
Windows Vista for x645.16.19.4 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.